examples: Reuse not_current_context
in resumed()
handler
#1687
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When testing the
glutin
example on Android, after suspending and resuming the app no triangle appears. As it turns out thewinit 0.30
bump in #1678 never reuses thenot_current_context
that was set apart insuspended()
, but creates a new one, without re-running initialization code such as creating theRenderer
.Partially restore original code before the
winit 0.30
bump, which never created a context inresumed()
because it was already available before the loop started (and moved back in place insuspended()
). Note also that more initialization code that now (unnecessarily) lives inresumed()
used to be outside of the loop.CHANGELOG.md
if knowledge of this change could be valuable to users